
<!DOCTYPE html>

<html lang="en">
  <head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="generator" content="Docutils 0.17.1: http://docutils.sourceforge.net/" />

    <title>Installing Leo &#8212; Leo 6.7.2 documentation</title>
    <link rel="stylesheet" type="text/css" href="_static/pygments.css" />
    <link rel="stylesheet" type="text/css" href="_static/classic.css" />
    <link rel="stylesheet" type="text/css" href="_static/custom.css" />
    
    <script data-url_root="./" id="documentation_options" src="_static/documentation_options.js"></script>
    <script src="_static/jquery.js"></script>
    <script src="_static/underscore.js"></script>
    <script src="_static/_sphinx_javascript_frameworks_compat.js"></script>
    <script src="_static/doctools.js"></script>
    <script src="_static/sphinx_highlight.js"></script>
    
    <script src="_static/sidebar.js"></script>
    
    <link rel="index" title="Index" href="genindex.html" />
    <link rel="search" title="Search" href="search.html" />
    <link rel="next" title="Running Leo" href="running.html" />
    <link rel="prev" title="Downloading Leo" href="download.html" /> 
  </head><body>
    <div class="related" role="navigation" aria-label="related navigation">
      <h3>Navigation</h3>
      <ul>
        <li class="right" style="margin-right: 10px">
          <a href="genindex.html" title="General Index"
             accesskey="I">index</a></li>
        <li class="right" >
          <a href="running.html" title="Running Leo"
             accesskey="N">next</a> |</li>
        <li class="right" >
          <a href="download.html" title="Downloading Leo"
             accesskey="P">previous</a> |</li>
        <li class="nav-item nav-item-0"><a href="leo_toc.html">Leo 6.7.2 documentation</a> &#187;</li>
          <li class="nav-item nav-item-1"><a href="getting-started.html" accesskey="U">Downloading, Installing &amp; Running Leo</a> &#187;</li>
        <li class="nav-item nav-item-this"><a href="">Installing Leo</a></li> 
      </ul>
    </div>  

    <div class="document">
      <div class="documentwrapper">
        <div class="bodywrapper">
          <div class="body" role="main">
            
  <section id="installing-leo">
<h1>Installing Leo<a class="headerlink" href="#installing-leo" title="Permalink to this heading">¶</a></h1>
<p>This chapter tells how to install and run Leo on Windows, Linux and MacOS.</p>
<p>These instructions look complicated because they’re long, but really they just boil down to:</p>
<ul class="simple">
<li><p>install python. Python 3.9 or later is required.</p></li>
<li><p>run <cite>pip install leo</cite> from a python enabled command prompt.</p></li>
<li><p>run leo from that same python enabled command prompt.</p></li>
</ul>
<p><strong>Important</strong>: If you have <em>any</em> problems installing Leo, please ask for help on <a class="reference external" href="http://groups.google.com/group/leo-editor">Leo’s help forum</a>.</p>
<div class="contents local topic" id="contents">
<p class="topic-title">Contents</p>
<ul class="simple">
<li><p><a class="reference internal" href="#dependencies" id="id1">Dependencies</a></p></li>
<li><p><a class="reference internal" href="#installing-leo-with-pip" id="id2">Installing Leo with pip</a></p>
<ul>
<li><p><a class="reference internal" href="#pypi-install-caveat" id="id3">PyPi install caveat</a></p></li>
</ul>
</li>
<li><p><a class="reference internal" href="#installing-packages" id="id4">Installing packages</a></p></li>
<li><p><a class="reference internal" href="#installing-leo-itself" id="id5">Installing Leo itself</a></p>
<ul>
<li><p><a class="reference internal" href="#installing-leo-on-windows" id="id6">Installing Leo on Windows</a></p>
<ul>
<li><p><a class="reference internal" href="#installing-from-sources-windows" id="id7">Installing from sources (Windows)</a></p></li>
<li><p><a class="reference internal" href="#creating-windows-file-associations" id="id8">Creating Windows file associations</a></p></li>
</ul>
</li>
<li><p><a class="reference internal" href="#installing-leo-from-sources-all-platforms" id="id9">Installing Leo from sources (all platforms)</a></p></li>
<li><p><a class="reference internal" href="#installing-leo-with-git" id="id10">Installing Leo with git</a></p></li>
<li><p><a class="reference internal" href="#installing-leo-on-macos-10-7-lion-and-later" id="id11">Installing Leo on MacOs 10.7 (Lion) and later</a></p></li>
</ul>
</li>
<li><p><a class="reference internal" href="#installing-everything-with-anaconda-or-miniconda" id="id12">Installing everything with Anaconda or Miniconda</a></p></li>
</ul>
</div>
<section id="dependencies">
<h2><a class="toc-backref" href="#id1">Dependencies</a><a class="headerlink" href="#dependencies" title="Permalink to this heading">¶</a></h2>
<p>Leo’s minimal dependencies are:</p>
<ul class="simple">
<li><p><a class="reference external" href="https://www.python.org/">Python</a> 3.9 or later.</p></li>
<li><p><a class="reference external" href="http://www.riverbankcomputing.com/software/pyqt/download5">PyQt5</a>.</p></li>
<li><p><cite>PyQtWebEngine</cite></p></li>
</ul>
<p>The following packages are optional, but recommended:</p>
<ul class="simple">
<li><p><a class="reference external" href="http://docutils.sourceforge.net">Docutils</a>: required for the rst3 command and the viewrendered plugins.</p></li>
<li><p><a class="reference external" href="http://www.sphinx-doc.org/en/stable/">Sphinx</a>: required to regenerate Leo’s documentation.</p></li>
<li><p><a class="reference external" href="http://pyenchant.github.io/pyenchant/install.html">PyEnchant</a>: required for spell checking.</p></li>
</ul>
<p>Plugins may require other packages.  For example, viewrendered requires <a class="reference external" href="http://daringfireball.net/projects/markdown/syntax">Markdown</a> if one wishes to use markdown rendering, but it is optional. rss.py will not function without <a class="reference external" href="https://pypi.python.org/pypi/feedparser">feedparser</a>. Etc.</p>
</section>
<section id="installing-leo-with-pip">
<h2><a class="toc-backref" href="#id2">Installing Leo with pip</a><a class="headerlink" href="#installing-leo-with-pip" title="Permalink to this heading">¶</a></h2>
<p>Python’s <a class="reference external" href="https://pypi.org/pypi/pip">pip</a> tool will download <em>and</em> install Leo and all of Leo’s dependencies automatically.</p>
<ol class="arabic">
<li><p><a class="reference external" href="http://python.org.">Install Python</a> first, if necessary. Make sure to install Python 3, not Python 2.</p></li>
<li><p>Check whether pip has been installed using the terminal window command below. If there’s an error <a class="reference external" href="https://pip.pypa.io/en/stable/installing/">Install pip</a>:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">pip</span> <span class="o">--</span><span class="n">version</span>
</pre></div>
</div>
</li>
</ol>
<p>In some circumstances using pip as a module works better:</p>
<blockquote>
<div><p>python -m pip –version</p>
</div></blockquote>
<ol class="arabic" start="3">
<li><p>Download and install Leo and all required packages from <a class="reference external" href="https://pypi.org/">PyPi</a>:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">pip</span> <span class="n">install</span> <span class="n">leo</span>
</pre></div>
</div>
</li>
</ol>
<p>or</p>
<blockquote>
<div><p>python -m pip install leo</p>
</div></blockquote>
<section id="pypi-install-caveat">
<h3><a class="toc-backref" href="#id3">PyPi install caveat</a><a class="headerlink" href="#pypi-install-caveat" title="Permalink to this heading">¶</a></h3>
<p>When Leo has been installed in non-editable mode* (the above) there will be messages in the log pane window when opening certain .leo files distributed with Leo, such as LeoDocs.leo. (_File &gt;&gt; Open Leo File &gt;&gt; …_). The warnings are not serious and may be ignored.</p>
<p>This is a known issue with no practical solution. Files in the root folder of the leo-editor code repository is not installed when using pip. This is because they need to be relative to <code class="docutils literal notranslate"><span class="pre">./leo-editor/leo</span></code> folder, which make them at the top of <code class="docutils literal notranslate"><span class="pre">PYTHONHOME/lib/site-packages</span></code>, and thus in the global namespace and not part of leo as far as python is concerned.</p>
<p>Details at <a class="reference external" href="https://github.com/leo-editor/leo-editor/issues/603">Missing files when installing Leo from PyPI using “pip install leo”</a>.</p>
<p>* An editable install is from source code, either a git clone or downloaded archive. See:</p>
<ul class="simple">
<li><p>An editable install is from source code, either a git clone or downloaded archive. See:</p></li>
</ul>
<ul class="simple">
<li><p>Installing Leo with git</p></li>
<li><p>Installing from sources (Windows)</p></li>
</ul>
</section>
</section>
<section id="installing-packages">
<h2><a class="toc-backref" href="#id4">Installing packages</a><a class="headerlink" href="#installing-packages" title="Permalink to this heading">¶</a></h2>
<p><strong>Python</strong>: Leo will work on any platform that supports Python 3.9 or above.
To install Python, see <a class="reference external" href="http://python.org">http://python.org</a>.</p>
<p><strong>PyQt</strong>: <a class="reference external" href="http://www.riverbankcomputing.co.uk/software/pyqt/intro">PyQt</a> provides Leo’s widgets:</p>
<ul class="simple">
<li><p>Download PyQt5 from <a class="reference external" href="http://www.riverbankcomputing.com/software/pyqt/download5">http://www.riverbankcomputing.com/software/pyqt/download5</a>.</p></li>
</ul>
<p><strong>Important</strong>: The PyQt version must match your installed Python version. Remember that Leo requires Python 3.9 or later.</p>
<p><strong>PyEnchant</strong>: You must install <a class="reference external" href="http://pyenchant.github.io/pyenchant/install.html">PyEnchant</a> if you want to use Leo’s Spell tab.</p>
</section>
<section id="installing-leo-itself">
<h2><a class="toc-backref" href="#id5">Installing Leo itself</a><a class="headerlink" href="#installing-leo-itself" title="Permalink to this heading">¶</a></h2>
<section id="installing-leo-on-windows">
<h3><a class="toc-backref" href="#id6">Installing Leo on Windows</a><a class="headerlink" href="#installing-leo-on-windows" title="Permalink to this heading">¶</a></h3>
<p>Install Python and Qt, as described above (<a class="reference internal" href="#installing-packages">Installing Packages</a>).</p>
<p>Now you have a choice.  You can use Leo’s binary (single-click) installer
or download Leo’s sources directly.</p>
<section id="installing-from-sources-windows">
<h4><a class="toc-backref" href="#id7">Installing from sources (Windows)</a><a class="headerlink" href="#installing-from-sources-windows" title="Permalink to this heading">¶</a></h4>
<p>Download Leo’s sources using one of the methods described at <a class="reference external" href="download.html">Leo’s download page</a>.</p>
<p>After download unpack the zip archive where you like and from a python enabled command shell:</p>
<blockquote>
<div><p>pip install –editable C:\path\to\leo-editor</p>
</div></blockquote>
<p>This will leave Leo where it is and and create launch scripts in
PYTHONHOME\Scripts.</p>
<p>Next see <a class="reference external" href="running.html">Running Leo</a> and then optionally come back here for <a class="reference internal" href="#creating-windows-file-associations">Creating Windows file associations</a>.</p>
</section>
<section id="creating-windows-file-associations">
<h4><a class="toc-backref" href="#id8">Creating Windows file associations</a><a class="headerlink" href="#creating-windows-file-associations" title="Permalink to this heading">¶</a></h4>
<p>From <em>Settings</em> menu select <strong>Open Desktop Integration</strong>.
The new Leo file that opens will add 4 buttons under the menu bar:</p>
<p><em>[Register-leo]</em> - Creates registry keys for Leo file type and .leo
file association. Afterwards .leo files will show Leo icon and
double-clicking them will open in Leo Editor.</p>
<p><em>[Unregister-leo]</em> - Removes the above.</p>
<p><em>[add-desktop-links]</em> - Creates launch shortcuts in desktop and system menu</p>
<p><em>[remove-desktop-links]</em> - Removes the launch shortcuts</p>
</section>
</section>
<section id="installing-leo-from-sources-all-platforms">
<h3><a class="toc-backref" href="#id9">Installing Leo from sources (all platforms)</a><a class="headerlink" href="#installing-leo-from-sources-all-platforms" title="Permalink to this heading">¶</a></h3>
<p>Generic recipe for all platforms. Adjustment for local norms is expected. For example <cite>7z</cite> could be <cite>unzip</cite> or interactive extraction and <cite>wget</cite> could be a browser download.</p>
<p>Linux: it’s generally advised to use pip <code class="docutils literal notranslate"><span class="pre">--user</span></code> flag instead of <cite>sudo</cite>.</p>
<p>Assumes <strong>Python 3.9 or later</strong> is installed and in PATH.</p>
<p>Installing from source code into a new environment must be done in discrete steps: <strong>download</strong>, <strong>unpack archive</strong>, and <strong>install as editable</strong> mode.</p>
<p>Example:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">wget</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">github</span><span class="o">.</span><span class="n">com</span><span class="o">/</span><span class="n">leo</span><span class="o">-</span><span class="n">editor</span><span class="o">/</span><span class="n">leo</span><span class="o">-</span><span class="n">editor</span><span class="o">/</span><span class="n">archive</span><span class="o">/</span><span class="n">devel</span><span class="o">.</span><span class="n">zip</span>
<span class="mi">7</span><span class="n">z</span> <span class="n">x</span> <span class="n">devel</span><span class="o">.</span><span class="n">zip</span> <span class="o">-</span><span class="n">o</span> <span class="n">C</span><span class="p">:</span>\<span class="n">apps</span>
<span class="n">pip</span> <span class="n">install</span> <span class="o">--</span><span class="n">editable</span> <span class="n">C</span><span class="p">:</span>\<span class="n">apps</span>\<span class="n">leo</span><span class="o">-</span><span class="n">editor</span><span class="o">-</span><span class="n">devel</span>
</pre></div>
</div>
<p>For easier upgrading substitute <code class="docutils literal notranslate"><span class="pre">git</span> <span class="pre">clone</span></code> for wget &amp; 7z steps:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">git</span> <span class="n">clone</span> <span class="o">--</span><span class="n">no</span><span class="o">-</span><span class="n">single</span><span class="o">-</span><span class="n">branch</span> <span class="o">-</span><span class="n">b</span> <span class="n">devel</span> <span class="o">--</span><span class="n">depth</span><span class="o">=</span><span class="mi">200</span> <span class="n">https</span><span class="p">:</span><span class="o">//</span><span class="n">github</span><span class="o">.</span><span class="n">com</span><span class="o">/</span><span class="n">leo</span><span class="o">-</span><span class="n">editor</span><span class="o">/</span><span class="n">leo</span><span class="o">-</span><span class="n">editor</span><span class="o">.</span><span class="n">git</span>
<span class="n">pip</span> <span class="n">install</span> <span class="o">--</span><span class="n">editable</span> <span class="n">leo</span><span class="o">-</span><span class="n">editor</span>
</pre></div>
</div>
<p>time passes, upgrade desired:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">pushd</span> <span class="n">c</span><span class="p">:</span>\<span class="n">apps</span>\<span class="n">leo</span><span class="o">-</span><span class="n">editor</span>
<span class="n">git</span> <span class="n">pull</span>
<span class="n">pip</span> <span class="n">uninstall</span> <span class="n">leo</span>
<span class="n">pip</span> <span class="n">install</span> <span class="o">--</span><span class="n">editable</span> <span class="o">.</span>
</pre></div>
</div>
<p><cite>b</cite> and <cite>depth</cite> are optional, but will dramatically speed up download time as it only grabs the latest development branch, the tips of other branches, and skips all but the last couple weeks or months of history.</p>
<p><strong>Note</strong></p>
<p>Direct <code class="docutils literal notranslate"><span class="pre">pip</span> <span class="pre">install</span> <span class="pre">https://github.com/leo-editor/leo-editor/archive/devel.zip</span></code> does <em>not</em> work. For proper operation Leo relies on presence of certain files outside of the standard Python <cite>site-packages</cite> folder structure.</p>
<p>See <a class="reference external" href="running.html">Running Leo</a> for how to run Leo after installing it.</p>
</section>
<section id="installing-leo-with-git">
<h3><a class="toc-backref" href="#id10">Installing Leo with git</a><a class="headerlink" href="#installing-leo-with-git" title="Permalink to this heading">¶</a></h3>
<p><strong>Important</strong>: This section tells how to set up <a class="reference external" href="https://git-scm.com/">git</a> so that you can grab
the latest sources using <code class="docutils literal notranslate"><span class="pre">git</span> <span class="pre">clone</span></code>.</p>
<p>Many users will want to track the development version of Leo, in order to stay
on top of the latest features and bug fixes. Running the development version is
quite safe and easy, and it’s also a requirement if you want to contribute to
Leo.</p>
<ol class="arabic">
<li><p>First, you need to get git from <a class="reference external" href="http://git-scm.com/">http://git-scm.com/</a>.</p></li>
<li><p>Get Leo from GitHub by doing:</p>
<blockquote>
<div><p><code class="docutils literal notranslate"><span class="pre">git</span> <span class="pre">clone</span> <span class="pre">--depth=500</span> <span class="pre">--no-single-branch</span> <span class="pre">https://github.com/leo-editor/leo-editor</span></code> (http access)</p>
<p>or:</p>
<p><code class="docutils literal notranslate"><span class="pre">git</span> <span class="pre">clone</span> <span class="pre">--depth=500</span>&#160; <span class="pre">--no-single-branch</span> <span class="pre">git&#64;github.com:leo-editor/leo-editor.git</span></code> (ssh access)</p>
<p>followed by checking out the _devel_ branch:</p>
</div></blockquote>
</li>
</ol>
<p><code class="docutils literal notranslate"><span class="pre">git</span> <span class="pre">checkout</span> <span class="pre">devel</span></code></p>
<ol class="arabic" start="3">
<li><p>Install dependencies and create leo script launcher:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">pip</span> <span class="n">install</span> <span class="o">--</span><span class="n">editable</span> <span class="n">path</span><span class="o">/</span><span class="n">to</span><span class="o">/</span><span class="n">leo</span><span class="o">-</span><span class="n">editor</span>
</pre></div>
</div>
</li>
</ol>
<p>And that’s it! You can run leo with <cite>PYTHONHOME/Scripts/leo</cite> or <cite>python leo-editor/launchLeo.py</cite>. When you want to refresh the code with latest modifications from GitHub, run <code class="docutils literal notranslate"><span class="pre">git</span> <span class="pre">pull</span></code>.</p>
</section>
<section id="installing-leo-on-macos-10-7-lion-and-later">
<h3><a class="toc-backref" href="#id11">Installing Leo on MacOs 10.7 (Lion) and later</a><a class="headerlink" href="#installing-leo-on-macos-10-7-lion-and-later" title="Permalink to this heading">¶</a></h3>
<p>Many thanks to Ludwig Schwardt for the following installation instructions. Using the HomeBrew installation method is <em>much</em> easier than before.</p>
<p><strong>Note from EKR</strong>: When upgrading MacOS, it’s probably a good idea to uninstall pyqt, sip and qt first:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">brew</span> <span class="n">remove</span> <span class="n">pyqt</span> <span class="n">sip</span> <span class="n">qt</span>
<span class="n">brew</span> <span class="n">install</span> <span class="n">qt</span> <span class="n">sip</span> <span class="n">pyqt</span>
</pre></div>
</div>
<p>I (Ludwig) recently received a new MacBook Pro and did a fresh upgrade to Mac OS 10.7 (Lion). I then used the opportunity to test out installation procedures of various software on a clean system. My main finding is that the excellent Homebrew (mxcl.github.com/homebrew/) makes things much easier these days.</p>
<p>Why Homebrew? It does not try to replace every single bit of functionality on your Mac with their own version, like Macports or fink. It reuses the existing libraries as far as possible. No need to reinstall Python, for example (one of my pet gripes when people try to install new software on their Macs, and the source of much confusion and pain). It installs to /usr/local, the standard place to find third-party libraries and headers, instead of the obscure /opt or /sw. It’s simple to use and to extend.</p>
<p>Here is my installation write-up:</p>
<ul>
<li><p>Read the Homebrew installation instructions at <a class="reference external" href="http://brew.sh/">http://brew.sh/</a>.</p></li>
<li><p>Make sure you have Xcode installed (test it by confirming that “gcc” runs in the Terminal) Only the smaller command-line tools are required; there is no need to get the full Xcode beast.</p></li>
<li><p>In preparation for Homebrew, the best option in my opinion is to delete /usr/local via:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">sudo</span> <span class="n">rm</span> <span class="o">-</span><span class="n">rf</span> <span class="o">/</span><span class="n">usr</span><span class="o">/</span><span class="n">local</span>
</pre></div>
</div>
<p>and install any software in it via HomeBrew instead.</p>
<p>The HomeBrew package manager is so easy to use that you will find replacing deleted packages a snap.</p>
<p>If deleting /usr/local fills you with dread (you do not want to lose your beloved third-party software), the second-best option is to make sure you have write permission for the directory via:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">sudo</span> <span class="n">chown</span> <span class="o">-</span><span class="n">R</span> <span class="o">&lt;</span><span class="n">your</span> <span class="n">user</span> <span class="n">name</span><span class="o">&gt;</span><span class="p">:</span><span class="n">admin</span> <span class="o">/</span><span class="n">usr</span><span class="o">/</span><span class="n">local</span>
</pre></div>
</div>
<p>If you don’t know your username, run “whoami”. :-) This is useful because homebrew actually discourages you from installing third-party software as the superuser (the usual Mac apps in /Applications are also installed as the normal user, for that matter).</p>
</li>
<li><p>Install Homebrew. See the instructions at <a class="reference external" href="https://brew.sh/">https://brew.sh/</a>.</p></li>
<li><p>Run “brew doctor” and check any further suggestions to improve your system.</p>
<p>EKR note: I thought I had installed command-line tools after installing the XCode page. I hadn’t, and “brew doctor” told me so.</p>
</li>
<li><p>Run “brew update” to get the latest formulas</p></li>
<li><p>Install sip and note the caveat:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">brew</span> <span class="n">install</span> <span class="n">sip</span>
</pre></div>
</div>
<p>This warns you to add the local python directory to your PYTHONPATH.
Make a note of what this is (especially if you are not on Lion!).</p>
</li>
<li><p>Add the following lines to your ~/.bash_profile
(or ~/.profile on Leopard). This is the default for LION:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>export PATH=/usr/local/bin:$PATH
# This is for SIP (and PyQt) as suggested by Homebrew
export PYTHONPATH=/usr/local/lib/python2.7/site-packages:$PYTHONPATH
</pre></div>
</div>
</li>
<li><p>Install PyQt:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">brew</span> <span class="n">install</span> <span class="n">pyqt</span>
</pre></div>
</div>
</li>
<li><p>Open a new Terminal tab / window so that the above settings take effect, and install Leo. I downloaded the Leo-4.9-final-a.zip, unzipped it, and ran “python launchLeo.py” inside the Leo directory.</p></li>
</ul>
<p>It would really be great to get a Leo formula going for Homebrew. As mentioned before, the main question is just where to place all the Leo files in the /usr/local hierarchy.</p>
</section>
</section>
<section id="installing-everything-with-anaconda-or-miniconda">
<h2><a class="toc-backref" href="#id12">Installing everything with Anaconda or Miniconda</a><a class="headerlink" href="#installing-everything-with-anaconda-or-miniconda" title="Permalink to this heading">¶</a></h2>
<p>The <a class="reference external" href="https://www.anaconda.com/download/">Anaconda</a> scientific computing environment includes Python, NumPy, SciPy, PyQt, and over a thousand other tools, packages and libraries. It’s a 500+ MB download but you’re guaranteed to have everything needed.</p>
<p>The <a class="reference external" href="https://conda.io/miniconda.html">Miniconda</a> environment includes just Python and the <cite>conda</cite> package management tool. Pick and choose from the full Anaconda ecosystem.</p>
<p>Preparation, create an environment for Leo, activate it, and then install python:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">conda</span> <span class="n">create</span> <span class="o">-</span><span class="n">n</span> <span class="n">leo</span>
<span class="n">conda</span> <span class="n">activate</span> <span class="n">leo</span>
<span class="n">conda</span> <span class="n">install</span> <span class="n">python</span>
</pre></div>
</div>
<p>Strictly speaking this step can be skipped and Leo installed in the conda _base_ environment. The conda developers generally advise against installing in _base_ unless this program is the only thing the machine will be used for.</p>
<p>To install Leo run this from a console:</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">pip</span> <span class="n">install</span> <span class="n">leo</span>
</pre></div>
</div>
</section>
</section>


            <div class="clearer"></div>
          </div>
        </div>
      </div>
      <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
        <div class="sphinxsidebarwrapper">
            <p class="logo"><a href="leo_toc.html">
              <img class="logo" src="_static/LeoLogo.svg" alt="Logo"/>
            </a></p>
  <div>
    <h4>Previous topic</h4>
    <p class="topless"><a href="download.html"
                          title="previous chapter">Downloading Leo</a></p>
  </div>
  <div>
    <h4>Next topic</h4>
    <p class="topless"><a href="running.html"
                          title="next chapter">Running Leo</a></p>
  </div>
<div id="searchbox" style="display: none" role="search">
  <h3 id="searchlabel">Quick search</h3>
    <div class="searchformwrapper">
    <form class="search" action="search.html" method="get">
      <input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
      <input type="submit" value="Go" />
    </form>
    </div>
</div>
<script>document.getElementById('searchbox').style.display = "block"</script>
        </div>
<div id="sidebarbutton" title="Collapse sidebar">
<span>«</span>
</div>

      </div>
      <div class="clearer"></div>
    </div>
    <div class="related" role="navigation" aria-label="related navigation">
      <h3>Navigation</h3>
      <ul>
        <li class="right" style="margin-right: 10px">
          <a href="genindex.html" title="General Index"
             >index</a></li>
        <li class="right" >
          <a href="running.html" title="Running Leo"
             >next</a> |</li>
        <li class="right" >
          <a href="download.html" title="Downloading Leo"
             >previous</a> |</li>
        <li class="nav-item nav-item-0"><a href="leo_toc.html">Leo 6.7.2 documentation</a> &#187;</li>
          <li class="nav-item nav-item-1"><a href="getting-started.html" >Downloading, Installing &amp; Running Leo</a> &#187;</li>
        <li class="nav-item nav-item-this"><a href="">Installing Leo</a></li> 
      </ul>
    </div>
    <div class="footer" role="contentinfo">
        &#169; Copyright 1997-2023, Edward K. Ream.
      Last updated on February 28, 2023.
      Created using <a href="https://www.sphinx-doc.org/">Sphinx</a> 5.3.0.
    </div>
  </body>
</html>